TMF639 10DLC Number Provisioning

In Mule applications, JSON Web Tokens (JWTs) serve as a secure method to authenticate clients. When a client attempts to access a protected resource, they must first present a JWT, typically obtained through a separate authentication process. This token acts as a compact, self-contained package containing the user's identity, along with additional metadata. The server, upon receiving a request with a JWT, validates this token by checking its integrity and authenticity by verifying the token's digital signature. Successful validation confirms the client's identity, allowing the application to determine if the request should proceed.

Following authentication, authorization determines what an authenticated client is allowed to do within the Mule application. JWTs facilitate this by embedding "claims" or assertions about the bearer and their permissions. These claims includes standard attributes defined in RFC 7519.

The TMF639 - 10DLC REST API uses JWT token to authenticate and authorize its clients.

The business number provisioning MUST be done using a compatible client. The sender-client compatibility is based on the NNID, assigned to the client and the same NNID assigned to the requested number in the Netnumber. For example: Using an Ouath token for a 10DLC sender when provisioning an 800 number will fail as NNID won't match.